Libris Britannia 4

home *** CD-ROM | disk | FTP | other *** search

/ Libris Britannia 4 / science library(b).zip / science library(b) / COMMUNIC / BULLETIN / 0457.ZIP / SYSMTXT.ROS < prev

Wrap

Text File | 1987-03-01 | 19KB | 431 lines

:WM - Welcome message Welcome to the Albuquerque ROS Steve Fox - Sysop 300/1200/2400 bps detected at connect by a Courier 2400 Modem from US Robotics 8 bit characters, 1 stop bit, no parity, full duplex Operating 24 hours per day at (505)299-5974 from Albuquerque, New Mexico All information and activities on this system must be legal. :GM - Goodbye message Thanks for calling, please call again. Adios.... :B0 - Bulletin automatically displayed at login -=*=- -=*=- -=*=- -=*=- -=[ BULLETINS ]=- -=*=- -=*=- -=*=- -=*=- 3/1/87 ROS version 3.61, correcting some problems with file transfers using Xmodem protocol, will be ready late this evening. Press... "?" for menus and help CTRL-S to pause listings Keys within "<>" for commands CTRL-C to cancel listings The number at the first of each system prompt is your access time remaining. -=*=- -=*=- -=*=- -=*=- -=*=- -=*=- -=*=- -=*=- -=*=- -=*=- -=*=- :B1 - User selected bulletin -=*=- -=*=- -=*=- -=*=[ Turbo User Group ]=*=- -=*=- -=*=- -=*=- Borland International says they have distributed over 500,000 copies of Turbo Pascal. Many programs for this excellent compi- ler are stored in the TPASCAL file area. Feel free to download these files and to upload any others you have found useful. If you are using Turbo Pascal, you may be interested in the Turbo User Group which publishes a bi-monthly magazine of hints, bugs, insights, and tutorials. The magazine is not large, but the material is worthwhile. Membership is $20.00. The address is: Turbo User Group (TUG) P.O. Box 1510 Poulsbo, Washington USA 98370 :B2 - User selected bulletin -=*=- -=*=- -=*=[ Remote Operating System - ROS ]=*=- -=*=- -=*=- The following briefly describes the features of ROS, an integra- ted message and file transfer system: General features: Written entirely in Turbo Pascal Does not require other support routines Fast user file access using B+ trees Individual access control for each user All functions selected by a single keystroke User functions: Send and receive public and private messages Multiple message areas Can access multiple file areas and libraries Sorted file directory File sizes shown in bytes or transfer time Supports Xmodem and Ymodem protocol (checksum and CRC) Send text files with automatic processing of "squeezed" files List special bulletins, system information, BBS lists, etc. Chat with sysop Change user parameters List names of other users on system Sysop functions: List, edit, purge, and recover user file List and purge messages and system log List and update NEWIN list List, edit, and use macros (pre-defined keystroke sequences) Build system directory Copy, move, and delete files Local login Local commands to disable remote, initiate chat, etc. :B3 - User selected bulletin -=*=- -=*=- -=*=- [ What's an Xmodem Anyway? ]- -=*=- -=*=- -=*=- Several times a day, as I pass the system and take a quick glance just to make sure that all is well, I see some messages pertaining to file transfers and that someone is having a problem or two getting the Xmodem routines to run. So perhaps a quick review of what's SUPPOSED to happen will help those that haven't used Xmodem file transfers much. First, two definitions: Sender: the computer system which will transmit information to the receiver, much like a radio station sends a signal to the radio receiver in our car. Receiver: the computer system which will accept or receive infor- mation from the sender. Using these definitions, then, when you ask ROS, which is running on THIS system, to send a file, ROS becomes the sender and your computer becomes the receiver. To make a file available for others, such as those in the NEWIN section, you will need to make YOUR machine the sender and ROS the receiver. The Xmodem (or Christensen) protocol is designed to produce error free file transfers by locking the sending and receiving machines together in such a way that any errors in a block or record are detected. When an error is found in this way, the receiving machine asks the sending machine to try again. This may happen several times in a single block, but usually the reason for the error is noise on the phone line that is gone when the block is re-sent. Consequently, the limit of 10 errors in a single block rarely causes a premature termination. In fact, most terminations occur in the first block, usually because the two machines never got synchronized. That interlock, so critical to the success of the protocol, is established when the receiving machine tells the sender that it is ready, but the sender MUST ALREADY BE WAITING FOR THAT ACKNOWLEDGEMENT. So, to get a file from ROS to your system, follow these steps: 1. Tell ROS to <S>end (from the Files sub-system). 2. Tell ROS which file you want. 3. ROS will verify that the file does exist and that you have enough access time to complete the transfer. If all goes well, ROS will announce the approximate time the transfer will take, and then say that it is ready for the transfer to begin. 4. Tell YOUR COMPUTER that you want it to RECEIVE a file. This usually involves some commands which include the file name and maybe the type of protocol (Xmodem) that will be used. The exact form of the command can be found in your documentation. 5. Your computer will then do some checking of its own. If all goes well, your computer will tell ROS that it's ready to receive and the transfer will proceed. 6. After the transfer is complete, ROS will return to normal command mode for your next instruction. To get a file from your system to ROS, follow these steps: 1. Tell ROS to <R>eceive (from the Files sub-system). 2. Tell ROS the name of the file you intend to send it. 3. ROS will make sure the file doesn't already exist and that the name is valid. If all goes well, ROS will announce the amount of disk space available, and then say that it is ready for the transfer to begin. 4. Tell YOUR COMPUTER that you want it to SEND a file. This usually involves some commands which include the file name and maybe the type of protocol (Xmodem) that will be used. Again, the exact form of the command will be found in your documenta- tion. 5. Your computer will then try to find the file. It it does, it starts waiting for ROS to say it's ready to receive. WHAT? ROS already said it was ready, right? Partially. ROS told YOU it was ready, but while you were telling your machine to send a file, ROS was counting to itself. About 4 seconds after ROS tells you it is ready, it starts sending a code that your computer will interpret as a ready signal. ROS will send this code several times before it finally gives up. 6. When your computer detects that ROS is ready, it starts sending the file. 7. When the transfer is complete, ROS will ask for a short description of the file you sent for the benefit of other users. That's where the information in the <N>ewin function comes from. While the terms "upload" and "download" aren't usually used in ROS, they correspond to <R>eceive and <S>end respectively, i.e. "upload" means to send a file from a remote system to a host (from you to ROS, so ROS is receiving), and "download" means to send a file from a host to a remote system (from ROS to you, so ROS is sending). In both cases, ROS is acting as the host sys- tem. For those interested in the technical aspects of the error checking, I'll just say that ROS will automatically detect cyclic redundancy code (CRC) or checksum modes during send operations (as requested by your machine), and that during receive opera- tions, ROS will try both modes until something works or it times out (preference is given to CRC for accuracy). :B4 - user selected bulletin -=*=- -=*=- -=*=- -=*=[ ROS-PC Version 3.6 ]=*=- -=*=- -=*=- -=*=- The ability to transfer (with Xmodem) files from within an archive has been added (sorry, can't <T>ype from them yet). A <W>hereIs function has been added to the files sub-system to assist in finding a particular file. Defaults to Yes/No questions are tailored to the specific question. Most common operations can now be performed without having to hunt for "Y" or "N". An accidental <G>oodbye can be recovered back to a system prompt. Response to ^S/^C is immediate for XON/XOFF transfers. For the sysop, many changes have been implemented to improve local and remote operations. -=*=- -=*=- -=*=- -=*=- -=*=- -=*=- -=*=- -=*=- -=*=- -=*=- -=*=- :OS - Other systems -=*=[ Other Remote Computer Systems in the Albuquerque Area ]=*=- Name Baud Number Sysop Hours System -------------- ------- -------- -------------- --------- ------- Albq. Heath 3/12/24 292-6770 Dave Alexander 24 hr ROS Albq. RBBS-PC 3/12/24 296-7672 John Maio 24 hr RBBS-PC Albq. ROS 3/12/24 299-5974 Steve Fox 24 hr ROS Academy BBS 3 296-4887 Brian Langdon 8pm-10am Hal BBS Applequerque 3/12 256-7357 ??? 24 hr Mac ??? 3 266-5150 Marty Lavens 24 hr Apple CBM BBS 3/12 822-1159 Bo Farley 24 hr Punter LL-Zee System 3/12 865-9036 Bob Williams 9pm-8am ROS Moonlight BBS 3 869-6820 Peggy Lawrence 3pm-6am C64 Xch NELT 3 294-3922 Drew Reidle 24 hr TRS NM DEC-PC RCPM 3/12 831-0205 Eloy Gonzales 24 hr ROS Online Albq. 3/12 $892-1111 Greg Sinkey 24 hr IBM-PC Outpost 3 877-3031 Dennis Massegee 24 hr C-64 ROS Connection 3/12 #266-0677 Jim Pattee 24 hr ROS TBC BBS 3/12/24 821-7379 Dave Staehlin 24 hr PC-Brd "$" by the phone number indicates systems that charge for access. "#" by the phone number indicates "ring back" systems. To call them, let the phone ring once or twice, hang up, and call back. More than 2 rings indicates a voice call. Please help fill in the areas of this list that have question marks. Leave corrections, deletions, and additions in a message to SYSOP. -=*=- -=*=- -=*=- -=*=- -=*=- -=*=- -=*=- -=*=- -=*=- -=*=- -=*=- :NF - Name search failed Old users: you may answer "N" to the following question to try again. If it has been some time since you last called, you may have been purged from the active user list, and will have to start again as a new user. New users: you may answer "Y" to the following question to be added to the user list. If you used a "handle," please answer "N" and enter your real name. :PF - Password match failed Since you have exceeded the number of attempts allowed to enter your password correctly, you will be given the opportunity to leave a message and then the system will disconnect. If you are local, leave your phone number and I will try to get in touch with you. :IN - Information for new users -=*=- -=*=- -=*=- [ Information for New Users ] -=*=- -=*=- -=*=- Please take the time to read the following carefully: The Albuquerque ROS is available 24 hours per day, primarily for computers using CP/M, MS-DOS, or PC DOS, but others are welcome. 60 Mbytes of storage are available on-line for messages and files. A Courier 2400 modem from U.S. Robotics automatically detects the transmission rate of 300, 1200, or 2400 bps at answer. This Remote Operating System (ROS) was written by Steve Fox using Turbo Pascal (from Borland International) with B+ tree indexed file support. Access to the operating system is not necessary for file transfer, since this is built into the system (see the File Transfer System menu). A user's guide to ROS is available in the LOGIN file area. This file, ROSUSR.DQC, may be either typed or downloaded using Xmodem protocol. If you have not used ROS before, please take the time to look at this file - several differences exist between ROS and other bulletin board systems. Unvalidated (new) users will be allowed 15 minutes per day. This should be enough time to get familiar with the system and deter- mine whether or not you wish to become a fully validated user. No charges are ever made for this system, nor are donations even encouraged, but because attempts have been made to use the system improperly, registration will be required for full access. Until this is done, all messages will be routed to the sysop and the number of files that can be accessed will be severely restricted (only the LOGIN file area will be available). You may register during the logout process or from the tility sub-system. Only your name will be known to other users. All other information will be strictly private and will not be used for any purpose other than validation (no mailing lists or the like) which is normally done in 48 hours. I apologize for any inconvenience these restrictions might cause you, but like locks on doors, they are necessary because of the few individuals that have abused the system. The first number in each system prompt indicates the amount of time available until the system will automatically log you out. -=*=- -=*=- -=*=- -=*=- -=*=- -=*=- -=*=- -=*=- -=*=- -=*=- -=*=- :RR - Registration request Only your name will be shown to other users. The following information will be strictly private and will not be used for any purpose other than validation (no mailing lists or the like), which is normally completed in 48 hours. :AR - Transfer from within an archive When this transfer is complete, you will have a standard archive with exactly one entry. Any archive utility may then be used to extract and decompress this entry into your file. :UD - Upload description Please enter a brief description of your file and the computer or operating system it runs on, e.g. MS DOS, CP/M-80, Amiga, etc: |------------------------------------------------| :HM - Help for message sub-system Albuquerque ROS - Message Sub-System ==== Functions ==== ==== Bulletins ==== == System Changes == <A>nswer last msg ulletin <G>oodbye (logoff) <C>hange msg area <1> Turbo User Group <F>ile Sub-System <D>elete a msg <2> ROS tility Sub-System <E>nter a msg <3> Xmodem nfo for new users <O>ther systems list <Q>uick-scan messages <R>ead messages <S>can messages e<X>pert mode toggle :HF - Help for file sub-system Albuquerque ROS - File Sub-System =============== Functions =============== == System Changes == <C>hange file area <F>ilesize display <G>oodbye (logoff) <D>irectory of files <N>ewin list <M>essage Sub-System <L>ibrary or archive open/close tility Sub-System <W>here is (file search) <R>eceive file using Xmodem protocol (you --> ROS) <S>end file using Xmodem protocol (ROS --> you) <T>ype ASCII or squeezed file (Xon/Xoff supported) e<X>pert mode toggle :HU - Help for utility sub-system Albuquerque ROS - Utility Sub-System =============== Functions =============== == System Changes == <A>lter configuration <S>tatistics <F>ile Sub-System <C>hat with sysop <T>ime and date <M>essage Sub-System <R>egister for access ser list <G>oodbye (logoff) e<X>pert mode toggle :HC - Help for system configuration Albuquerque ROS - System Configuration ell after prompt <H>elp level assword change <C>haracters/line <L>ines/page <S>hift lock <D>efault areas <N>ulls after newline <T>ransfer protocol All parameters will be retained from one call to the next. :HS - Help for sysop Sub-system Albuquerque ROS - Sysop Sub-System =============== Functions =============== == System Changes == <A>udit trail toggle <O> Macro operations <F>ile Sub-System <C>opy file urge files <M>essage Sub-System <D>elete file <R>edirect file tility Sub-System <E>dit user record <S>ystem directory <J>ump to DOS <T>oggle printer <G>oodbye (logoff) <L>ist system files e<X>pert mode toggle <N>ewin file edit :HE - Help for editing text ======= Text Editing Functions ======= === Editor Commands === CTRL-A Move cursor one word left <C>ontinue text entry CTRL-S Move cursor one character left <E>dit a selected line CTRL-D Move cursor one character right <L>ist current text CTRL-F Move cursor one word right <S>ave text to disk TAB Space to next tab position <Q>uit without saving Backspace, RUB, or DEL Delete character left of cursor CTRL-G Delete character at cursor CTRL-X Delete line left of cursor RETURN Complete line entry New characters are inserted into the existing line. If there are characters to the right of the current cursor position, they will be moved over to make space. Insertions will not be shown until the line is explicitly re-listed. :HT - Help for transfer mode selection ROS, in conjunction with your telecommunications software, sup- ports two methods of error detection during file transfers: cyclic redundancy check (CRC) and checksum. Either may be used with short (128 byte) blocks, but CRC is enforced when transfer- ring long (1024 byte) blocks. You may let ROS try to determine the best protocol, or select your preference. In either case, ROS will try to adjust if it detects incompatible modes. For example, if you ask ROS to send a file using checksum, but your system is set to use CRC, the file transfer will still succeed since ROS will switch to CRC as well. Similarly, if you tell ROS to receive using Xmodem CRC but your system starts sending long blocks, ROS will accommodate. :HP - Help for purge file command <A>ll <L>og <M>essage <N>ewin ser <Q>uit :HL - Help for list file command <A>ll <L>og <M>essage <Q>uit :HR - Help for edit user record <D>elete <E>dit <N>ext revious <R>egistered <S>elect <V>alidate <Q>uit :HA - Help for alter message status <D>elete ndividual (private) <M>ove ublic <R>ead :HN - Help for change status of files listed in NEWIN <A>dd <D>elete <E>dit <H>ide <R>elease <Q>uit :HI - Help for information displayed during user listing <A>ll <E>xceptional <Q>uick nvalidated <H>ide <R>elease <Q>uit :HI - Help for information displayed during user